[SELC-6133] feat: added attribute attachments into response for API v2/tokens/{onboardingId} #378
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 3 commits
December 9, 2024 09:58
…backend into feature/SELC-6133 � Conflicts: � connector/rest/docs/openapi/api-selfcare-onboarding-docs.json
pierpaolodidato89
temporarily deployed
to
dev-cd
GitHub Actions
Inactive
pierpaolodidato89
temporarily deployed
to
dev-ci
GitHub Actions
Inactive
|
pierpaolodidato89
temporarily deployed
to
dev-cd
GitHub Actions
Inactive
pierpaolodidato89
temporarily deployed
to
dev-cd
GitHub Actions
Inactive
andrea-putzu
approved these changes
Dec 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
List of Changes
Added attribute attachments into response for API v2/tokens/{onboardingId}
Motivation and Context
This change is necessary to provide list of attachments linked to an onboarding.
How Has This Been Tested?
I have deployed the feature branch in DEV and tested the API GET v2/tokens/{onboardingId}
Screenshots (if appropriate):
Checklist: